\section*{Task Assignments}

Over the course of the quarter, it was decided that the Android App
really needed more attention to it than we had originally planned. In
response to that change, we added responsibilities of the Android App
to Andrew and Jesse as well released Kevin from worrying about a lot
of the documentation, aside from his code. The majority of time was
spent working on the Android App and integrating the web front end to
the back end.  Trinh has spent days without much sleep making sure
everything is working properly. Cody was busy helping Trinh with the
web application, as well as making sure everyone else was on
track. Once the database was set up and working, Chris spent most of
his time modifying the database interface to be more customer
friendly, as well as partly keeping the team on track with the
releases. Once we discovered the lag on the Android App development,
Kevin, Jesse, and Andrew all started focusing more intently on
bringing it back to where it needed to be.

Once the App was brought back up to speed, Andrew and Jesse continued
their work on the application as well as their work on the ACH and
AndroidServer, respectively. We chose to do this to ensure that the
app didn't fall behind again as more features were being added and the
time to add them was lessening. In terms of what we originally
planned, we were able to stick to our plan fairly well.  We were
expecting team members to switch to the Android App, however it had to
happen sooner than we expected. This turned out to be a good thing as
it gave more brain power to the portion of the product that was the
most obscure.  One unexpected problem, though, was how much work the
web platform turned out to be due to the difficulty of writing sound
Javascript code.

At the start of the project, there was not enough time spent working
on the Android App, as mentioned repeatedly, as well as there was not
enough time spent working on automated unit and integration tests,
which was why we had some interesting integration bugs that took
longer to debug than they should have.  Another area where the wasn't
enough time put into it was focusing on few use cases in the
beginning. Our setup allowed for each portion to be built in parallel,
which also allowed for each part to have the basics of every use case,
however when they were integrated, there were bugs in all of them, and
instead of focusing on one area, we focused on all of the bugs at the
same time.

Too much time was spent on working on scattered bugs instead of fixing
a specific subset of them. Time was also spent focusing on the
database when other portions needed work. The latter part of the
project, Chris seemed to have extra time as well as maintaining the
database that could have been used in other places. Other than that,
There wasn't enough time in the quarter to spend it all in one
portion, so our problem was that we didn't think we ever had enough
time to do all of it.